The Universal XML Organizer: UXO

The integrated editor UXO is the result of ongoing research and development of the text-technology group at Bielefeld. Being a full featured XML-based editing system, it also allows to combine the structured annotated data with information imported from relational databases by integrating a JDBC interface. The mapping processes between different levels of annotation can be programmed either by the integrated scheme interpreter, or by extending the functionality of UXO using the predefined Java API. 1. System architecture The integrated editor UXO is the result of ongoing research and development of the text-technology group at Bielefeld. The system is an integrated XML-based text editor, which is configurable to a large degree and can so be easily adapted to specific user needs. The editor has been implemented in Java making it possible to execute it on a large number of platforms. UXO allows to enter the data either by typing in text or by working directly on the displayed structure tree. The structure can be validated by starting the inbuild XML parser (XML4J, IBM). In contrast to standard XML tools available, UXO offers an integrated interface to relational databases in combination with a build-in interpreter for the scheme programming language, used as the systems scripting language. This combination allows to configure the editor for a wide range of varying applications simply by defining control/configuration scripts. As these scripts are external to editor, reconfiguration does not mean to recompile the system. More experienced programmers are able to extend the permanent features of UXO using the powerful API. In principle this API allows to integrate any Java functionality available (see also Reinsch and Milde (2000), Milde (1999)). The editor manages the full Unicode character set (Unicode, 1996). Its graphical user interface can be completely reconfigured allowing to localize the software and define appropriate control key sequences. Figure 1 shows the basic system architecture. Internally all data is handled as a DOM instance. It is possible to map database requests (via JDBC, see Klute (1998)), servlet requests (via HTTP) and XML documents onto this model. The editor allows to modify the content of a document and to validate its structure. Figure 1: The basic architecture of the system: DOM is used as a central data structure. Database requests, servlet requests and XML-annotated documents are mapped onto a DOM which can then be edited using the UXO editor. Mapping rules are defined using the buildin scripting language (scheme). Alternatively UXO can be extended using the Java API.